home *** CD-ROM | disk | FTP | other *** search
- it requires System 7.x
-
- the symbolics file was not found
-
- the System does not have enough memory
-
- the symbolics file is the wrong version
-
-
-
- a %_MethTables parsing error
-
- a Sym File error
-
- it could not be found
-
- the specified type could not be found in the SYM file
-
- the task is unknown
-
- the team is unknown
-
- the task is running
-
- the task is not running
-
- there was an access error
-
- there was a system call error
-
- there was a trap instruction error
-
- there was a floating point exception error
-
- there was an invalid instruction error
-
- there was a privileged instruction error
-
- there was an instruction trace error
-
- there was an instruction address compare error
-
- there was a data trace error
-
- there was a data address compare error
-
- there was a nub debugging error
-
- of an unknown register
-
- of an unknown breakpoint
-
- there are too many breakpoints
-
- of a wrong task breakpoint
-
- of an unknown CPU
-
- of an inconsistent step stack
-
- of a step stack overflow
-
- the port is not available
-
- of a driver buffer overflow
-
- of a driver buffer underflow
-
- the driver ISR init failed
-
- of an unknown info selector
-
- of an empty exceptions list
-
- of an unknown exception type
-
- or a verify error while trying to write memory
-
- the library was not found
-
- the process was not found
-
- the container was not found
-
- the section was not found
-
- the PC is not valid
-
- the symbol was not found
-
- of a bad system info selector
-
- the extension was not found
-
- the loader event notify failed
-
- of an unknown loader event
-
- of an unexpected loader event
-
- you are trying to set a breakpoint in ROM
-
- the specified pattern could not be found in memory
-
- of an unknown error
-
- of a communication error (other side too old)
-
- of a communication error (this side too old)
-
- of a communication error (string is corrupt)
-
- of a communication error (packet too large)
-
- of a communication error (transmission failed)
-
- of a communication error (unknown failure)
-
- of a communication error (odd packet offset)
-
- of a communication error (large packet offset)
-
- of a communication error (packet too small)
-
- of a communication error (packet too large)
-
- of a communication error (odd packet length)
-
- of a communication error (bad packet arguments signature)
-
- of a communication error (null packet callback function)
-
- of a communication error (send failed)
-
- of a communication error (receive failed)
-
- of a communication error (packet corrupt)
-
- of a communication error (timed out)
-
- of a communication error (unexpected packet type)
-
- of a communication error (too many corrupt packets)
-
- of a communication error (too many Nub retries)
-
- of a communication error (too many NAKs)
-
- of a communication error (unexpected sequence)
-
- of a communication error (unexpected nub request)
-
- of a communication error (too many retries)
-
- of a communication error (bad header checksum)
-
- of a communication error (bad data checksum)
-
- of a communication error (bad data length)
-
- of a communication error (send NAK failed)
-
- of a communication error (no packet available)
-
- of a communication error (not connected)
-
- of a communication error (got NAK)
-
- that functionality has not been implemented by the nub
-
- of a PPC Toolbox error (PPCToolBox not initialized)
-
- of a PPC Toolbox error (Invalid or inappropriate locationKindSelector in locationName)
-
- of a PPC Toolbox error (Unable to open port or bad portRefNum)
-
- of a PPC Toolbox error (The system is hosed, better re-boot)
-
- of a PPC Toolbox error (Network activity is currently disabled)
-
- of a PPC Toolbox error (Port does not exist at destination)
-
- of a PPC Toolbox error (Out of session tables, try again later)
-
- of a PPC Toolbox error (Invalid session reference number)
-
- of a PPC Toolbox error (Bad parameter or invalid state for operation)
-
- of a PPC Toolbox error (Port is already open (perhaps in another app))
-
- of a PPC Toolbox error (User name unknown on destination machine)
-
- of a PPC Toolbox error (Destination rejected the session request)
-
- of a PPC Toolbox error (User hasn't named their Macintosh in the Network Setup Control Panel)
-
- of a PPC Toolbox error (A system resource is missing, not too likely)
-
- of a PPC Toolbox error (Unable to contact destination)
-
- of a PPC Toolbox error (Port was closed)
-
- of a PPC Toolbox error (Session was closed)
-
- of a PPC Toolbox error (PPCPortRec malformed)
-
- of a PPC Toolbox error (User hasn't typed in owners name in Network Setup Control Panel)
-
- of a PPC Toolbox error (The default userRefNum does not yet exist)
-
- of a PPC Toolbox error (Unable to create a new userRefNum)
-
- of a PPC Toolbox error (An error has occured in the network, not too likely)
-
- of a PPC Toolbox error (PPCStart failed because destination did not have inform pending)
-
- of a PPC Toolbox error (Unable to authenticate user at destination)
-
- of a PPC Toolbox error (Invalid user reference number)
-
- of a PPC Toolbox error (Illegal service type, or not supported)
-
- of a PPC Toolbox error (Location name malformed)
-
- of a PPC Toolbox error (Target machine does not allow guest access)
-
- the PPC IO Primitives say there is no PPC Toolbox available
-
- the PPC IO Primitives ran out of buffer space
-
- the PPC IO Primitives says we are not connected anymore
-
- there was a data breakpoint address error
-
- there was a bad perf node iterator
-
- there was a bad perf bucket iterator
-
- the PPC IO Primitives say there is no PPC Toolbox available
-
- the PPC IO Primitives ran out of buffer space
-
- there is no PPCToolbox connection
-
- there was a page fault
-
- there was a write protection fault
-
- the address space is inaccessible
-
- there was a data breakpoint fault
-
- there was a data breakpoint range error
-
- there are too many data breakpoints set
-
- there was a data breakpoint type error
-
- there were too many threads requested
-
- the thread was not found
-
- there was a thread protocol error
-
- there was no type information in the variable
-
- there is not enough memory available
-
- of a user abort while waiting for target communication to complete
-
- the selected port is in use
-
- parameter RAM not configured for this connection
-
- this is not supported by the nub
-
-